General method of operation

On the basis of the specification of the infrastructure contained in the (master) test plan, it is considered whether further specifi cation and detail are necessary. The planning of the test environment, test tools and workplace is also worked out in more detail. Besides describing what resources are necessary, expectations are also set out in respect of the supplying party during the management of these resources. The timely involvement of the various parties is essential. Agreements should be made for the supply and build of the infrastructure, and these agreements should be checked at regular intervals. In consultation with the various suppliers (internal and external) it is determined how detailed the specification should be. The delivery times of the various parts are included in the detailed plan.

Workplace method of operation

The specification of the workplace covers tangible subjects, such as required locations, desks, chairs, telephones, PCs, et cetera. But it also covers less tangible things, such as required authorisations, disk space, software, e-mail accounts, et cetera. The realisation of these aspects may take a considerable amount of time. Occasionally it requires a special setup (e.g. project rooms) or special installation (e.g. the PCs). In other cases, items have to be ordered. It is advisable to emphasise at this stage specific requirements that are set in respect of management of the workplace. For example, obtaining separate status for the testers in the solving of problems in the workplace. This can be useful, since testers are no ‘ordinary users’ and sometimes require a different kind of support.

Test environment method of operation

In specifying the test environment, the various elements of the test environment should be considered. Definitions can vary among suppliers and organisations. For that reason, it should always be discussed clearly what is meant by particular terms. Another important point is the number of test environments required and the various types there are. Each type of test environment has its own purpose, with specific requirements applying to it.

The specifying of the technical form of the test environment should be done in consultation with someone who has technical knowledge of the environments. This individual should translate the concrete requirements (based on the aim of the test served by the test environment) into the technical form. As a basis for this, an architectural overview can be created, for example. This can be a difficult process, since two worlds (testing and technology) speak two different languages. It is up to the test-team individual responsible (the test manager or test infrastructure coordinator) to check whether this is organised satisfactorily.

Besides requirements concerning the setup of the test environment, requirements should be set in respect of the maintenance of it. Examples of requirements are:

• The backup activities that have to be carried out
• The comprehensibility of the software versions present
• The interfaces present
• The ability to change the test environment
• The ability to change the system date
• The use and management of test data
• Authorisations and their administration
• The required timetable for the building of a test environment.

Agreements should also be made at this point on how the test environment will be tested (see also the activity intake of the infrastructure). Other agreements may concern the contact with suppliers (direct by the test team or via another party) and how to deal with licences.

In some organisations, a standard set of test environments is used and the test manager has to use these for his test. If that is the case, during this activity he investigates the specific characteristics of these test environments and how they fit within the test.

Test tool method of operation

If, in the creation of the (master) test plan, it is decided to employ test tools, this should be firmed up during this activity. The decision should be backed up by definite choices of one or more tools. As made clear in the definition of test tools, they are intended to support one or more test activities. During this specification of the test tools, it should be clear which test activities are to be supported and how this should be done.

The selection and deployment of a tool can be carried out according to the life cycle model.

Products

• Detailed specification of workplace
• Detailed specification of test environment
• Test tool(s) plan of approach.